In Groovy, defining a property implicitly defines JavaBeans-style accessor methods (getters/setters). Frameworks and tools that rely on JavaBeans
conventions assume properties are named in camelCase so that accessor names are predictable.
When a property name starts with an uppercase letter or contains underscores, the generated accessor names can be surprising and inconsistent with
what other code expects. This reduces readability and can lead to integration issues (for example, with data binding, serialization, or
reflection-based frameworks).
What is the potential impact?
Non-camelCase property names can make code harder to understand and can break or complicate integrations with libraries that expect standard
JavaBeans naming.
